• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    MEDICAL SYSTEM, APPLIANCE AND METHODThe present invention relates to a centralized frequency agility technique that is employed with a plurality of medical body area network (MBAN) systems (10, 35, 36), each of which comprises a plurality of network nodes ( 12, 14) intercommunicating via short-range wireless communication. A central network (20, 22, 23, 24) communicates with MBAN systems through longer-range communication that is different from short-range wireless communication. A central frequency agility subsystem (40) is configured to communicate with MBAN systems. The central frequency agility subsystem receives the current channel quality information for a plurality of channels available for short-range wireless communication, and allocates the MBAN systems among the available channels based on at least the current quality information received .
    公开号:BR112012025263A2
    申请号:R112012025263-1
    申请日:2011-03-15
    公开日:2020-07-14
    发明作者:Dong Wang；Hongqiang Zhai；Monisha Ghosh
    申请人:Koninklijke Philips Electronics N.V.；
    IPC主号:
    专利说明:

    MEDICAL SYSTEM, APPLIANCE AND METHOD
    DESCRIPTION The present invention relates to medical monitoring techniques and related techniques.
    A medical body area network (MBAN) replaces the tangle of cables tying hospital patients to their bedside monitoring units with wireless connections. This provides low-cost wireless patient monitoring (PM - pacient monitoring) without the inconvenience and safety hazards posed by wired connections, which can trip medical personnel or loosen up in order to lose medical data. In the MBAN approach, low cost multiple sensors are connected in different locations on or around a patient, and these sensors read the patient's physiological information such as the patient's temperature, pulse, blood glucose level, electrocardiographic data ( ECG - electrocardiographic), or so on. The sensors are coordinated by at least one hub or gateway device to form the MBAN. The hub or gateway device communicates with the sensors using built-in short-range wireless radios, for example, conforming to an IEEE 802.15.4 (Zigbee) short-range wireless communication protocol. The information collected by the sensors is transmitted to the hub or gateway device via MBAN's short-range wireless communication, thus eliminating the need for cables. The hub or gateway device communicates the collected patient data to a central patient monitoring station (PM) via a wired or wireless connection with greater range for centralized processing, display and storage. The longest range network may, for example, include wired Ethernet and / or wireless protocol such as
    Wi-Fi or some proprietary wireless network protocol.
    The PM station may, for example, include a database of the electronic patient record database, display devices located at a nurses' station or elsewhere in the medical facility, or so on. monitoring the MBAN acquires the patient's physiological parameters.
    Depending on the type of parameter and the state of the patient, the data acquired can vary from important (for example, in the case of monitoring a healthy patient who is undergoing a regimen to obtain good health status) to critical health (for example, in the case of a critically ill patient in an intensive care unit). In general, there is a need for strict confidence in MBAN's wireless connections due to the medical content of the data.
    Short-range wireless communication networks such as MBAN systems tend to be susceptible to interference.
    The spatially distributed nature and, typically, the ad hoc formation of short-range networks can lead to substantial spatial overlap of different short-range networks.
    The number of short-range communication channels allocated to short-range communication systems is also typically limited by government regulation, type of network, or other factors.
    The combination of overlapping short-range networks and limited spectral space (or number of channels) can result in collisions between transmissions from different short-range networks.
    These networks may also be susceptible to radio frequency interference (RFI) from other sources, including sources that are not similar to short-range network systems.
    It is known to employ - frequency agility mechanisms to mitigate RFI in short-range networks. For example, in IEEE 802.15.4 (Zigbee) systems, clear channel assessment (CCA) can be used to identify a clean channel for communication and to avoid communication on a busy channel or on a channel that is susceptible to RFI from other sources. In the Bluetooth system, "random frequency alternation is used to mitigate possible interference from other coexisting networks. Other approaches include direct sequence spectrum (DSSS) spreading protocols and prior protocol verification. A complementary approach is to perform error checking of reported data, for example, using checksum testing or so on. If the reported data fails in error checking, it can be retransmitted to ensure accuracy.
    These techniques are generally effective for short-range network communication applications that can tolerate some error and / or transmission delay. Different MBAN systems, depending on their applications, usually have a different tolerance for transmission and delay errors. MBAN systems for fitness and wellness applications in general are able to tolerate such transmission errors and delay. However, MBAN systems for high accuracy monitoring usually carry critical life medical data and, therefore, have little or no error tolerance, and are also not susceptible to transmission delays, as can be introduced by retransmission. Transmission delays are problematic for such MBAN systems, because in communicating life-critical data delays can delay the detection of the onset of a life-threatening condition. In addition, the sensor nodes of an MBAN system are preferably small (for patient comfort) and of minimal complexity (to increase reliability and reduce manufacturing cost). Sensor nodes, therefore, typically have limited integrated data storage, so a life-critical parameter continuously monitored, such as ECG data, must be quickly transmitted out of the sensor node to avoid losing data. The following provides new and improved devices and methods that have overcome the problems mentioned above and others.
    According to one aspect disclosed, a medical system comprises: a plurality of medical body area network (MBAN) systems, each MBAN system comprising a plurality of intercommunicating network nodes via short-range wireless communication; a central network communicating with MBAN systems via long-range communication that is different from short-range wireless communication; and a central frequency agility subsystem configured to communicate with MBAN systems, the central frequency agility subsystem receiving current channel quality information for a plurality of channels available for short-range wireless communication and allocation of MBAN systems between the available channels based on at least the channel quality information received.
    According to another aspect disclosed, a method comprises: collecting current channel quality information for a plurality of channels usable by a plurality of medical body area network (MBAN) systems for short-range communication between system network nodes MBAN; and determining the MBAN systems between the channels based at least on the quality information of the current channel collected.
    An advantage lies in the secure coexistence of multiple MBAN systems that can overlap in space.
    Another advantage is the reduced or eliminated likelihood of transmission delays within or from an MBAN system.
    Another advantage lies in the reduced or eliminated likelihood of loss of critical medical data acquired by an MBAN system.
    Another advantage lies in the principle of assigning short-range communication channels of varying quality to MBAN systems in accordance with the criticality of data acquired by the various MBAN systems.
    Other advantages will be evident to those skilled in the subject after reading and understanding the following detailed description.
    FIGURE 1 schematically illustrates a medical body area network (MBAN) system in the context of a medical environment including a central frequency agility subsystem as disclosed herein.
    FIGURE 2 schematically illustrates an ordered list of available channels properly generated by the central frequency agility subsystem of Figure 1.
    FIGURE 3 schematically illustrates the initial processing flow in the central frequency agility subsystem of Figure 1 and in the MBAN system of FIGURE 1, how these systems are initialized.
    FIGURE 4 schematically illustrates the processing flow in the central frequency agility subsystem of FIGURE 1 responsive to a request to assign a communication channel to a new MBAN system.
    Referring to Figure 11, a medical body area network (MBAN) 10 includes a plurality of nodes in network 12, 14. At least one of the nodes in network 12, 14 serves as a hub device 14. Network nodes 12 communicate with the hub device 14 via a short-range wireless communication protocol.
    MBAN 10 is also sometimes referred to in the relevant literature by other equivalent terms, such as a body area network (BAN - body area netwotk), a body sensor network (BSN - body sensor network), a personal area network ( PAN - personal area network), an ad hoc mobile network (MANET - mobile ad hoc network), or so on - the term medical body area networks (MBAN) 10 is to be understood as encompassing these various alternative terms.
    Illustrative MBAN 10 includes four illustrative network nodes 12, 14, including hub device 14; however, the number of network nodes can be one, two, three, four, five, six or more, and in addition, the number of network nodes may in some embodiments increase or decrease in an ad hoc way as sensors are added or removed from the network to add or remove medical monitoring capability.
    Network 12 nodes are typically sensor nodes that acquire physiological parameters such as heart rate, respiration rate, electrocardiographic data (ECG), or so on; however it is also contemplated for one or more of the nodes of the network to perform other functions, such as the controlled delivery of a therapeutic drug through a skin patch or an intravenous connection, performing cardiac pacemaker functionality, or so on .
    A single network node can perform one or more functions.
    The illustrative network nodes 12 are arranged on the outside of a patient P; associated, however, more generally, the network nodes can be arranged on the patient, or on the patient (for example, a network node can take the form of an implanted device), or close to the patient within the communication range of the short-range communication protocol (for example, a network node may take the form of a device mounted on an intravenous infusion pump (not shown) mounted on a rod that is kept close to the patient, and in this case, the data of the monitored patient may include information such as intravenous fluid flow rate). It is sometimes desirable for network nodes to be made as small as possible to promote patient comfort, and to be of lesser complexity to increase confidence - therefore, such network nodes 12 are typically low power devices (to maintain battery or other small source of electrical power) and may have limited limited data storage or data storage. As a consequence, network nodes 12 must be in continuous or near-continuous short-range wireless communication with the hub device 14 in order to quickly transmit acquired patient data to the hub device 14 without overflowing the data buffer.
    Hub device 14 (also sometimes referred to in the relevant literature by other equivalent terms as "gateway device" or "hub node") coordinates the operation of MBAN 10 by collection (via Zigbee, Bluetooth ", or another communication protocol without short-range wire) the patient data acquired by the sensors of the network nodes 12 and transmits the collected data away from the MBAN 10 via a longer range communication protocol. The short range wireless communication protocol preferably has a relatively short operating range of a few tens of meters, a few meters, or less, and in some embodiments it adequately employs an IEEE 802.15.4 (Zigbee) short-range wireless communication protocol or a variant thereof, or a communication protocol wireless short-range Bluetooth "or a variant thereof. Both Bluetooth "and Zigbee operate on a frequency spectrum of about 2.4 to 2.5 GHz. Although Bluetooth" and Zigbee are suitable achievements for short-range wireless communication, other short-range communication protocols, including proprietary communication protocols are also contemplated. In addition, short-range wireless communication can operate at frequencies other than the range of
    2.4 to 2.5 GHz, with ranges in hundreds of mega-hertz, giga-hertz, dozens of giga-hertz, or other ranges. The short-range communication protocol must have sufficient reach for the hub device 14 to reliably communicate with all nodes in network 12 of the MBAN 10 system. In FIGURE 1, this short-range wireless communication is schematically indicated by the oval dot used to outline the MBAN 10 system. Short-range wireless communication is typically two-way, so network nodes 12 can communicate information (for example, patient data, network node status, or so on) forward) for hub device 14; and the hub device 14 can communicate information (e.g., commands, control data, in the case of a therapeutic network node, or so on) to the network nodes 12. The illustrative hub device 14 is a wrist-mounted device ; however, the concentrating device can be mounted in another way for the patient, for example, as a gluing device, the glued adhesive device, or so on. It is also contemplated for the hub device to be mounted at another location close to the patent, as being integrated with an intravenous infusion pump (not shown) mounted on a rod that is kept close to the patient. Hub device 14 also includes a transceiver (not shown) providing the longest-range communication capability for data communication outside the MBAN 10. In the illustrative example in Figure 1, hub device 14 communicates wirelessly with an access point ( AP - access point)
    20 of a hospital network 22. Illustrative AP 20 is a wireless access point that communicates wirelessly with hub device 14. In illustrative realization of hospital network 22 it also includes additional access points, such as illustrative AP access points 23 and AP 24, which are distributed throughout the hospital or other medical facility.
    To provide additional illustration, a nurse station 26 is schematically indicated, which is in wireless communication with the AP 24 and includes a monitor 28 that can, for example, be used to display medical data for patient P that are acquired by the MBAN 10 system and communicated to the nurses station 26 through the path comprising the AP 20, the hospital network 22 and the AP 24. Through another illustrative example, the hospital network 22 can provide access with an electronic subsystem of patient records 30 in which medical data are stored for patient P that are acquired by the MBAN 10 system and communicated to the electronic subsystem of patient records 30 through the path that comprises the AP 20 and the hospital network 22. The most extensive illustrative communication between the hub device 14 and the AP 20 is wireless, as schematically indicated in Figure 1 by a dashed connection line. (Similarly, wireless communication between the AP 24 and the nurse station 26 is indicated by a dashed connection line). In some suitable embodiments, the longest-range wireless communication is suitably a Wi-Fi communication link that conforms to an IEEE 802.11 wireless communication protocol or a variant thereof.
    However, other wireless communication protocols can be used for longer range communication, such as another type of wireless medical telemetry system (WMTS). In addition, the longest communication can be a wired communication such as a wired Ethernet connection (in which case the hub device includes at least one cable providing the longest wired communication link). Longer range communication is longer range compared to shorter range communication between network nodes 12 and hub device 14. For example, while shorter communication can be in the order of a few tens of centimeters, a few meters, or at most a few tens of meters at most, the longest reach communication typically comprises a substantial portion of the hospital or other medical facility using multiple access points 20, 23, 24 or, equivalently, multiple Ethernet sockets distributed throughout the hospital , in the case of a longer-range wired communication.
    Longer range communication, if wireless, requires more power than shorter range communication - in this sense, hub device 14 includes a battery or other sufficient power source to operate the longest range communication transceiver.
    Alternatively, hub device 14 may include a wired electrical connection.
    The hub device 14 also typically includes sufficient integrated storage so that it can maintain a substantial amount of patient data in the event that communication with the AP 20 is interrupted for some time.
    In the illustrative case of communication of greater reach, it is also to be understood that if patient P moves out of reach of AP 20 and to reach another AP (for example, AP 23 or AP 24), then the IEEE 802.11 or another wireless communication protocol contracted by hospital network 22 (including its wireless access points 20, 23, 24), provides for the wireless connection to change from AP 20 to the next new AP.
    In this regard, although patient P is illustrated as lying on a bed B, more generally it is contemplated for patient P to be an outpatient and to vary in and out of the various ranges of access points 20, 23, 24. As patient P thus moves, MBAN 10 including nodes in network 12 and hub device 14 moves with patient P.
    In MBAN 10, network nodes 12 communicate with the hub device 14 via short-range wireless communication. However, it is also contemplated for several pairs or groups of network nodes 12 to also intercommunicate directly (that is, without using the hub device 14, as an intermediary), through short-range wireless communication. This can be useful, for example, to coordinate the activities of two or more network nodes in time. In addition, hub device 14 may provide additional functionality - for example, hub device 14 may also be a network node that includes one or more sensors for measuring physiological parameters. In addition, while the single hub device 14 is illustrated, it is contemplated for the coordination functionality (for example, the collection of data from network nodes 12 and downloading of the data collected through the longer range wireless communication) to be incorporated by two or more nodes networks that cooperatively perform coordination tasks.
    In illustrative FIGURE 1, only the single MBAN 10 system is illustrated in detail. However, it will be appreciated that a more general way of the hospital or other medical facilities includes a plurality of patients, each having their own MBAN system. This is shown schematically in FIGURE 1 by two additional MBAN 35, 36 systems also in communication with the AP 20 via the longer range wireless communication. More generally, the number of MBAN systems can be, through some illustrative examples: two, three, four, five, ten, twenty, or more. In fact, it is still contemplated for a single patient to have two or more different MBAN systems that operate independently (not shown). In this environment, several MBAN systems can be expected to occasionally come in close proximity to each other, such that the ranges of the respective short-range wireless MBAN systems overlap.
    In addition, the hospital or other medical facility usually has several sources of radio frequency interference (RFI), such as magnetic resonance (MR), image scanners, computed tomography (CT) systems ), radiation therapy systems, wireless radios on cell phones and computers, radio equipment for communicating with ambulances, emergency helicopters, the local police, fire or other rescue workers and so on. As a consequence, the various MBAN systems must be allocated channels for their short-range communication in a manner that substantially avoids non-MBAN RFI and in a manner that substantially avoids interference between nearby MBAN systems.
    It is revealed here to employ a central frequency agility (CFA) subsystem 40 for this purpose of assigning short-range communication channels to MBAN systems in a way that substantially avoids non-MBAN RFI and in a way that substantially avoids interference between adjacent MBAN systems. The CFA 40 subsystem does not employ distributed frequency agility techniques as is usually the case with Zigbee, Bluetooth ", or other ad hoc short-range wireless communication networks, but centralizes frequency agility processing. The centralized approach disclosed here takes advantage of the existence of the longer centralized communication network 20, 22, 23, 24, which is available at the hospital or other medical facility and with which the MBAN systems are configured to communicate. By employing the centralized CFA 40 subsystem for implement frequency agility, it is possible to provide assignment of principles of short range communication channels of variable quality to MBAN systems in accordance with the criticality of the data acquired by the different MBAN systems, for example, although all MBAN systems are expected to collect important medical data, some MBAN systems can collect life-critical medical data (or, as other example, can offer life-sustaining therapeutic intervention); whereas, other MBAN systems can collect medical health data from patients who are undergoing wellness treatment as a fitness regime. By centralizing frequency agility, it is possible to assign these MBAN systems involved in life critical operations to the cleanest channels (in the sense of the potential for RFI interference and current channel quality information), and to allocate less critical MBAN systems to channels to a lesser extent (but still acceptable).
    The CFA 40 subsystem operates in an area within which MBAN systems can reasonably be expected to interfere with each other and / or experience non-ordinary MBAN RFI. For large medical facilities, such as a multi-storey hospital, more than one CFA subsystem can be provided, with the CFA subsystems distributed throughout the medical facility, in order to provide frequency agility for the various regions of the facility. In an appropriate approach, each AP 20, 23, 24 is provided with its own CFA subsystem - as an illustrative example, the CFA 40 subsystem in FIGURE 1 is assumed to be associated with the AP 20 and to perform frequency agility for MBAN 10, 35, 36 and any other MBAN systems that communicate with the AP
    20. In such realizations, the CFA 40 subsystem can be realized by the AP 20 processor running software suitable to implement the CFA 40 subsystem. Alternatively, the CFA 40 subsystem can be incorporated by another processor communicating with the AP 20, over the network hospital 22. In addition, a single CFA subsystem can perform centralized frequency agility for MBAN systems communicating with two or more access points, or for other suitable groupings of MBAN systems.
    The CFA 40 subsystem receives channel quality information (CQI) for the channels that are usable for the short-range wireless MBAN system. Current CQI information can be collected from various sources. In some realizations , MBAN 10, 35, 36 perform clean channel assessment (CCA) to generate the current coI information. Additionally or alternatively, a dedicated spectrum monitoring device 44 (or a spatial distribution of such devices) can be provided to acquire COI information. The spectrum monitoring device 44 or the devices are optionally powered by AC so that they have no batteries to be replaced or recharged. The CCA is properly performed by energy detection ( ED) or bearer of reading or other appropriate CCA operations to generate in-band interference information for the channels. the CQI may also include the detection of MBAN packets (for example, using a high-gain antenna) to acquire information about current activity on the channels, including estimation of transmission duty cycles. CQI information may also include analyzing the potential for “in-band” interference to assess sources of interference (for example, 802.15.4,
    802.11b / g, Bluetooth ", or so on). The COI information acquired by the MBAN 10, 35, 36 systems and / or the spectrum monitoring device 44 or devices is communicated to the CFA 40 subsystem through the larger communication reach, so that CQI information can be centrally collected in the CFA 40 subsystem. The CFA 40 subsystem allocates MBAN systems 10, 35, 36 among the available channels based on at least the current COI information received. be based on other information, such as an RFI rating for each channel, which indicates the likelihood of non-MBAN interference on that channel, and a quality of service (QoS - quality of service) for MBAN 10, 35 systems, 36. This latter information, if available, is used to influence the assignments of channels with the best current CQI (and, optionally, indicative ratings of least likely RFI) for MBAN systems with super ratings QoS values. For example, in an illustrative MBo QoS classification scheme, there are M classifications, with the highest QoS class (ie, Class 1) being reserved for MBAN systems involved in life critical applications, and the lowest of QoS class (ie Class M) used for non-critical applications, such as fitness monitoring. The QoS class of an MBAN system can be assigned by a doctor, nurse or other medical personnel when the MBAN system is created. Additionally or alternatively, the QoS class of an MBAN system can be automatically assigned based on the application running on the MBAN system. In the latter case, the MBAN system is appropriately assigned to its class based on the most critical application to be performed by the MBAN system.
    To illustrate diagrammatically, FIGURE 1 schematically shows a QoS MBAN 46 class assigned to the MBAN 10 system. (It is to be understood that the other MBAN 35, 36 systems each have also assigned a QoS MBAN class). The channels are also optionally assigned IRF ratings.
    These ratings are distinct from the current CQI for the channel, because the RFI rating is not based on current measurements or in MBAN usage, but rather is based on the likelihood of no MBAN RFI occurring on the channel.
    For example, in a suitable RFI rating scheme, there are 1, ..., N levels of IRF rating with level 1 RFI rating assigned to channels least likely to not MBAN RFI and level N assigned to channels with the highest probability of not MBAN RFI.
    As a more specific example, the interior of M-band channels, which are reserved especially for MBAN applications and are expected to have the smallest non-MBAN RFI, can be assigned RFI level 1. On the other hand, RFI Level N is for channels MBANs that are most likely to be interfered with by other wireless systems, and may include ISM channels that overlap with the 2.4GHz ISM Wi-Fi channel.
    In some embodiments, MBAN RFI assessments are predefined and stored in a database accessible by the CFA 40 subsystem. In the illustrative embodiment, the CFA 40 subsystem maintains a database of channels 48 that lists, for each channel, its availability, its current use (that is, that MBAN systems are assigned to the channel and, at least in the case of shared channels, their operating cycles), the current CQI for the channel and the RFI classification of the channel.
    The availability of a channel indicates whether the channel can be used by MBAN systems.
    A channel can be mentioned as unavailable for several reasons: its current CQI may be so poor that it cannot be used by MBAN systems; or the channel may be available for MBAN use on a secondary basis and is currently in use by a non-MBAN primary user; or so on.
    The database of channels 48 can have various formats and can store channel information in several different ways.
    As an illustrative embodiment, the structure of the following table can be used: Table (Field: channel number, The MBAN channel number Field: channel rating The channel's RFI rating Field: channel status: 'Inactive' if no MBAN uses this channel, otherwise 'busy' Field: active MBAN list This field is empty if the channel status is “inactive”, otherwise it is a subtable, which includes the information of MBANs active in the channel.) Subtable (Field: MBAN id, The MBAN id number Field: MBAN QoS class Field: Duty cycle The aggregate task cycle of this MBAN Field: Relative timing The synchronization relative to the AP device.
    This field is optional when the superstructure is used for MBANs and inter-MBAN synchronization is used to improve the efficiency of using the channel. )) With continued reference to FIGURE 1 and with additional reference to FIGURE 2, to facilitate the efficient operation of MBAN 10, 35, 36 systems, in some embodiments, a summary copy of the database of channels 48 is constructed by the subsystem of CFA 40 and is communicated to MBAN systems.
    In illustrative FIGURE 1, this is schematically illustrated by an ordered list 50 of available channels that has been communicated to and is stored in the MBAN 10 system. (It is understood that copies of the ordered list 50 are also stored in each of the other MBAN systems. 35, 36). FIGURE 2 schematically shows the ordered list 50 in greater detail.
    The ordered list 50 of channels is selected at least in the current CQI of the channel, and in the illustrative embodiment, the ordered list 50 is second selected in the RFI classification of the channel.
    The ordered list 50 includes only those channels that are available for use in MBAN systems of at least one MBAN class.
    In the illustrative example: the CQI class of the “Clean” channel is usable for MBAN class 1 MBAN systems (for example, life critical applications) and is listed first in the ordered list 50; “Acceptable” channel CQI class is usable for all MBAN systems except MBAN class 1, and is listed below in the ordered list 50; and finally the “Poor” channel CQI class is considered unusable for any MBAN system of any type and is therefore not included in the ordered list 50. The database of channel 48 is updated and the ordered list 50 updated and sent back to MBAN 10, 35, 36 systems on a regular basis.
    One approach to building the ordered list 50 is as follows.
    Input parameters include the measured COI channel (in terms of non-MBAN-interference-plus-noise power) for all usable channels (including channels that can be listed as not available in database 48). The channel CQI is determined based on the channel quality information measured by the MBAN systems 10, 35, 36 and / or by the optional dedicated spectrum monitoring device (s) 44. The Input parameters also optionally include the radio frequency spectrum used by current active non-MBAN wireless networks.
    This information could come from a database (not shown) accessible by the CFA 40 subsystem, for example through the hospital network 22. Such a database may, for example, include empirical measurement data and / or information based on RFI classified spectral spectrum of electronic devices in the hospital.
    This information can also be realized in the channel's RFI ratings - for example, if a hospital's MRI system is known to generate strong RFI on a particular channel, that channel may receive an RFI rating reflecting the expected high probability of experiencing RFI of the hospital's MRI system.
    Another optional input is the RF spectrum to be protected.
    For example, if a band is allocated on a secondary basis and there are some primary active users on that band, then the RF spectrum used by active primary users currently should not be allocated to any of the MBAN systems.
    This information can be generated by the CCA with knowledge of the secondary allocation status of the channel for MBAN systems.
    The selection algorithm is then suitably as follows.
    First, all channels in the RF spectrum to be protected should be omitted from the ordered list 50. (This adequately avoids having MBAN systems using the spectrum currently used by primary users). Second, group the channels by the classification of RFI i, i = l to N.
    For the channels of each RFI classification, group the channels within three CQI: clean ',' acceptable 'and' dirty '”. One way to do this is that if the non-MBAN-interference-plus-noise power is greater than a “dirty” limit then mark the channel as having a 'dirty /' current CQI; in addition, if the non-MBAN-interference-more-noise power is less than a “clean” threshold (and the channel is not in the RF spectrum used by current active non-MBAN wireless networks) then mark it how clean '; furthermore, mark it as 'acceptable'. Any channels that are marked with a 'dirty' channel CQI ”are considered unavailable for allocation to MBAN networks and are consequently omitted from the ordered list 50. Finally, the remaining channels having 'clean' or 'acceptable' channel CQI are selected based on the non-MBAN-interference-plus-noise power in an ascending order, and the results are combined to build the ordered list of available channels 50 as shown in FIGURE 2.
    The ordered list 50 of available channels can be used in several ways by the MBAN 10 system. For example, in performing CCA, the MBAN 10 system optionally collects CQI information for only those channels listed in the ordered list 50. This approach increases efficiency by avoiding CCA on channels that are unavailable. As another application, in the case of RFI interference or collision on the currently allocated channel, the MBAN 10 system can refer to the ordered list 50 to identify a suitable “clean” (or 'acceptable' channel, in the case of MBAN QoS class 46 being non-critical to life) with which the MBAN 50 system can exchange in order to avoid RFI or collision. This local relocation decision is then directed to the CFA 40 subsystem for entry into the channel 48 database. If the local relocation decision is determined to be unacceptable by the CFA 40 subsystem, appropriate remedial action must be taken.
    Having described suitable achievements of the centralized frequency agility system with reference to FIGURES 1 and 2, some additional operational aspects are determined with further reference to the flowcharts of FIGURES 3 and 4.
    With reference to FIGURES 1 and 3, starting procedures for initially energizing the AP 20 and MBAN 10 are determined. When the AP 20 is powered, its CFA 40 subsystem and associated database of channel 48 are initialized in an operation 60. The ordered list of available channels 50 is also properly generated based on the predefined channel RFI ratings. The channel usage status table is initialized by setting all available channels to 'INACTIVE'. In an operation 62, the channel CQI information transmitted to the AP 20 of the MBAN 10, 35, 36 systems and / or the monitoring device (s) 44 via the longest communication are used to initialize or update the values of the channel CQI in the channel 48 database, and the cumulative information in the channel 48 database is used to allocate MBAN systems on available channels having channel CQI compatible with the MBAN QoS classes. Operation 62 is updated when additional channel CQI information is received, as indicated by loop 64.
    Operation 62 is performed with CCA or other CQI information acquisition performed by the MBAN 10, 35, 36 and / or monitoring device (s) 44, as schematically shown for the illustrative MBAN 10 system. In FIGURE 3 , MBAN 10 energizes in an operation 70 and receives the ordered list of 50 channels through the longest communication in an operation 72. The following MBAN 10 system performs CCA or other acquisition of channel CQI information in an operation 74, and the CQI information is transmitted to the CFA 40 subsystem via the longest reach communication for use in operation 62 as schematically indicated in FIGURE 3 when connecting arrow 76. In an operation 78, the MBAN 10 system sends a request for a new allocation to the CFA 40 subsystem via a longer range communication, and in an operation 80, the MBAN 10 system receives the new channel allocation from the CFA 40 subsystem, again via the longer range communication , ec MBAN operation begins.
    With continued reference to FIGURES 1 and 3 and with additional reference to FIGURE 4, operation 78 generates a new MBAN 84 channel allocation request that is processed by the CFA 40 subsystem as shown in FIGURE 4. The new MBAN channel 84 has an associated MBAN class parameter indicating the MBAN 10 QoS class of MBAN 10 to which the new channel should be allocated.
    In an operation 86, the CFA 40 subsystem searches the channel 48 database for an available empty channel.
    In this context, “empty” means that the channel status information in the usage status table is' Inactive ”” and also the CCA 74 performed by MBAN 10 also showed the channel to be “inactive”. If operation 86 identifies a empty channel available, then the CFA 40 subsystem allocates MBAN 10 to that channel in an 88 operation, and sends the channel allocation response to MBAN 10 hub device 14 with the selected empty channel number.
    MBAN 10 starts operations on the allocated channel (this corresponds to the receive-and-operate operation 80 performed on MBAN 10), and MBAN 10 optionally sends back a channel assignment confirmation to the CFA 40 subsystem. CFA 40 updates the channel 48 database with the new channel assignment in an operation 90. On the other hand, if there is no “empty” channel available, then the CFA 40 subsystem performs an operation 92 in which it searches through a channel
    "busy! in the database of channel 48 that is in use by an existing MBAN system having a lower QoS class than the new MBAN 10 system. If such a" busy! channel is found, the CFA 40 subsystem sends command to the MBAN system operating on that 'busy' channel and reallocates it to other lower (but still acceptable) channel CQI channels, and the CFA 40 subsystem has allocated the MBAN 10 system to the vacant channel and accompanies with the update of the operating database 90. The 'other channel' to which the pre-existing MBAN system of lower MBAN QoS class is relocated could be a 'busy' channel already in use by one or more other MBAN systems, provided that the sum of your aggregate task cycles is less than some limit to ensure that there is no significant increase in the probability of collision caused by relocation.
    In the extreme case that there are many MBAN systems stacked together, the CFA 40 subsystem can generate a warning message for system administrators.
    When an active MBAN system moves into the service area of the AP 20, it will transfer and connect to the AP 20. This MBAN system continues to work properly on its current short-range wireless communication channel, but also reports its current channel allocation, its MBAN QoS class, and its task cycle aggregated to the AP 20's CFA 40 subsystem. The CFA 40 subsystem determines whether the new MBAN system operating on its current channel could cause increased potential collision on that channel.
    If not, then the CFA 40 subsystem updates the channel 48 database to reflect the use of the channel by the newly participating MBAN system.
    On the other hand, if the probability of collision is increased, the channel has an RFI rating indicative of a high probability of RFI, or is otherwise unacceptable, then the subsystem of
    CFA 40 performs the process of FIGURE 4 to allocate a new channel to the newly participating MBAN system.
    If an MBAN system detects degradation in channel quality and cannot work properly, for example, due to non-MBAN RFI or collision with short range wireless communication from a nearby MBAN system on the same channel, then the system MBAN relocates properly the local channel in order to switch to a new channel.
    This local channel reallocation is suitably based on the CCA performed by the MBAN system and based on the copy of the and ordered list of available channels 50 stored in the MBAN system.
    Such local channel reallocation ensures that an MBAN system can quickly switch to a new channel, and can thus prevent the loss of potentially critical medical data.
    However, the local channel reallocation is provisional.
    The MBAN system reports the local channel reallocation to the CFA 40 subsystem, which determines whether the local channel reallocation is acceptable based on the information contained in the centralized channel database 48. If the local channel reallocation is not acceptable, then the CFA 40 subsystem performs the process of FIGURE 4 to allocate a new channel to the MBAN system, in order to effectively “master” the local channel reallocation.
    With continued reference to FIGURE 1 and with additional reference again to FIGURE 3, the CFA 40 subsystem optionally performs a periodic relocation operation of the MBAN 94 system. This operation is performed in a centralized update of the MBAN system's channel allocations, and can (by way of example) move MBAN systems having the highest MBAN QoS class to the best quality channels (as measured by the current channel CQI and channel RFI rating) and exchange MBAN systems having smaller MBo QoS classes for other lower quality channels available.
    The periodic relocation operation 94 ensures that MBAN systems are optimally allocated among the available channels.
    When an MBAN system moves out of the service area of the AP 20, or when an MBAN system served by the AP 20 is turned off, then the AP 20 CFA 40 subsystem properly removes the channel usage information for that system MBAN number of the channel 48 database. This request described one or more preferred embodiments.
    Modifications and changes can occur to others by reading and understanding the previous detailed description.
    It is intended that the application be constructed as including all such modifications and changes to the extent that they fall within the scope of the appended claims or the equivalents thereof.
    权利要求:
    Claims (15)
    [1]
    1. MEDICAL SYSTEM, characterized by comprising: a plurality of systems of the medical body area network (MBAN) (10, 35, 36), each MBAN system (10) comprising a plurality of network nodes (12, 14) intercommunicating through short-range wireless communication; a central network (20, 22, 23, 24) communicating with the MBAN systems through longer-range communication that is different from short-range wireless communication; and a central frequency agility subsystem (40) configured to communicate with MBAN systems, the central frequency agility subsystem receiving current channel quality information for a plurality of channels available for short-range wireless communication and allocating the MBAN systems among the available channels based at least on the current channel quality information received.
    [2]
    2. APPLIANCE, as defined in claim 1, characterized in that each MBAN system (10) includes a plurality of network nodes (12) communicating with a hub device (14) by means of a short-range wireless communication, the hub device communicating with the central network (20, 22, 23, 24) through the longest range communication.
    [3]
    APPLIANCE, according to either of claims 1 or 2, characterized in that the central frequency agility subsystem (40) allocates the MBAN systems among the available channels still based on the classifications of (i) radio frequency interference for the channels and (ii) the quality of service ratings (46) of the MBAN systems.
    [4]
    4, APPARATUS, according to claim 3, in which responsive to receive a new channel allocation request from an unallocated MBAN system (10), the central frequency agility subsystem (40) performs a method characterized by understanding : the allocation of the unmanaged MBAN system to an available channel that is empty as long as there is an empty channel available having a radio frequency interference rating compatible with a quality rating of the unmanaged MBAN system and if there are no empty channels available having a radiofrequency interference rating compatible with the service quality rating of the unallocated MBAN system, then the relocation of an MBAN system already in operation having a service quality rating lower than the service quality rating MBAN system service not allocated to another channel and allocating the MBAN system not allocated to the vacant channel by realoc action.
    [5]
    5. APPLIANCE according to any one of claims 1 to 4, characterized in that the MBAN systems (10, 35, 36) are configured to: acquire current channel quality information for the plurality of available channels and send the information of current channel quality acquired to the central frequency agility subsystem (40) through the communication of greater reach.
    [6]
    6. "APPLIANCE according to any one of claims 1 to 5, characterized in that it additionally comprises: at least one spectrum monitoring device (44) configured to: acquire current channel quality information for the plurality of available channels and send the current channel quality information acquired from the central frequency agility subsystem (40) through the longer range communication.
    [7]
    Apparatus according to any one of claims 1 to 6, characterized in that the central frequency agility subsystem (40) is configured to: build an ordered list (50) of available channels that is selected at least by the information of current channel quality for the available channels and send the ordered list of available channels to the plurality of MBAN systems (10, 35, 36) by means of the longest communication.
    [8]
    APPARATUS, according to claim 7, characterized in that the central frequency agility subsystem (40) omits from the ordered list (50) of available channels any channel that has current channel quality information indicating that the channel quality current is too poor to be used by any MBAN system (10, 35, 36).
    [9]
    Apparatus according to either of claims 7 or 9, characterized in that the central frequency agility subsystem (40) omits from the ordered list (50) of available channels any channel that is available to MBAN systems (10, 35, 36) on a secondary basis and is currently in use by a non-MBAN primary user.
    [10]
    10. APPARATUS, according to any one of claims 7 to 9, characterized in that the MBAN systems (10, 35, 36) are configured to: acquire current channel quality information for only the available channels listed in the ordered list ( 50) of available channels and send the current channel quality information acquired to the central frequency agility subsystem (40) through the longest communication.
    [11]
    11. APPARATUS, according to any one of claims 1 to 10, characterized in that: the central network (20, 22, 23, 24) includes wireless communication of greater range implemented by a plurality of spatially distributed access points ( 20, 23, 24); and the central frequency agility subsystem (40) allocates the MBAN systems (10, 35, 36) allocated to a common access point (20) among the available channels.
    [12]
    12. METHOD, characterized by understanding: the collection of current channel quality information for a plurality of channels usable by a plurality of medical body area network (MBAN) systems (10, 35, 36) for short-range communication among network nodes (12, 14) of the MBAN systems; and the allocation of MBAN systems between channels based on at least the current channel quality information collected.
    [13]
    13. METHOD, according to claim 12, characterized in that the allocation is additionally based on the quality of service classifications (46) of the MBAN systems (10, 35, 36).
    [14]
    14. METHOD according to either of claims 12 or 13, characterized in that it further comprises: the construction of an ordered list (50) of available channels based on at least the current channel quality information for the channels; and the communication of the ordered list of channels available to the MBAN systems (10, 35, 36), in which the MBAN systems generate the current channel quality information that is collected by the collection operation only for the channels in the ordered list of available channels.
    [15]
    15. METHOD according to any one of claims 12 to 14, characterized in that it further comprises: the construction of an ordered list (50) of available channels based on at least the current channel quality information for the channels; the communication of the ordered list of channels available to the MBAN systems (10, 35, 36); and performing a local channel reallocation in an MBAN system based on the ordered list of communicated channels available.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012025263A2|2020-07-14|medical system, apparatus and method
    US9992685B2|2018-06-05|Medical body area network | with key-based control of spectrum usage
    JP6430829B2|2018-11-28|MBAN channel usage control scheme and adaptive channelization for the IEEE 802.15.4J standard
    US9094781B2|2015-07-28|Spectrum reallocation with prioritized schedule
    JP6097227B2|2017-03-15|Measures to enforce indoor spectrum usage supported by backhaul links for MBAN services
    JP5785606B2|2015-09-30|Medical Body Area Network | with automatic use of spectrum in facilities
    JP6050206B2|2016-12-21|Radiation imaging system and communication environment control apparatus
    US20130316652A1|2013-11-28|Method to use auxiliary channel to achieve fast and power-efficient association in wireless networks
    JP2012519521A|2012-08-30|Improvement of body area network
    Ullah et al.2019|Traffic priority based delay-aware and energy efficient path allocation routing protocol for wireless body area network
    Yuce et al.2007|A wireless medical monitoring over a heterogeneous sensor network
    Gama2011|A MAC protocol for quality of service provisioning in adaptive biomedical wireless sensor networks
    de Almeida Gama2011|A MAC Protocol for Quality of Service Provisioning in Adaptive Biomedical Wireless Sensor Networks
    同族专利:
    公开号 | 公开日
    US20130023214A1|2013-01-24|
    RU2012146974A|2014-05-27|
    EP2556697A1|2013-02-13|
    CN102823293A|2012-12-12|
    EP2556697B1|2018-05-16|
    RU2576475C2|2016-03-10|
    JP2013524667A|2013-06-17|
    WO2011124995A1|2011-10-13|
    CN102823293B|2015-12-09|
    JP5797258B2|2015-10-21|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    JP3109504B2|1998-03-27|2000-11-20|日本電気株式会社|Cellular system, method for avoiding adjacent frequency interference in cellular system, and mobile station|
    EP1732338A4|2004-03-05|2011-06-29|Ntt Docomo Inc|Frequency channel assigning system, base station, control station, inter-system common control apparatus, frequency channel assigning method and control method|
    TWI258276B|2004-11-25|2006-07-11|Inst Information Industry|Dynamic channel allocation for wireless access points and wireless networks|
    US20060224048A1|2005-03-22|2006-10-05|Aware Technologies, Inc.|Wearable personal area data network|
    GB2429875B|2005-09-05|2008-03-12|Toshiba Res Europ Ltd|Improved broadband carrier frequency selection|
    US7580682B2|2005-12-02|2009-08-25|Robert Bosch Gmbh|Method and apparatus for comprehensive link assessment and frequency monitoring in wireless sensor networks|
    JP2008053889A|2006-08-23|2008-03-06|Matsushita Electric Ind Co Ltd|Handover method, base station, terminal station, program recording medium and integrated circuit|
    KR100928678B1|2006-10-02|2009-11-27|삼성전자주식회사|Method and device for controlling connection admission in broadband wireless access system|
    JP4946596B2|2007-04-23|2012-06-06|日本電気株式会社|Radio resource allocation apparatus and method|
    KR101398359B1|2007-07-31|2014-05-26|삼성전자주식회사|Method for switching channels through which contenst data is received in zigbee network system and the zigbee network system|
    GB2457432A|2008-01-28|2009-08-19|Fujitsu Lab Of Europ Ltd|Mitigating interference in wireless communication systems|
    US8190167B2|2008-09-29|2012-05-29|Intel Corporation|Wireless device channel selection using dynamic channel allocation|
    US8478282B2|2008-10-20|2013-07-02|Centurylink Intellectual Property Llc|Method and apparatus for managing frequencies used by devices|
    US8305917B2|2009-03-23|2012-11-06|Motorola Solutions, Inc.|System and method for maintaining a backup radio operating parameter list in a secondary use communication system|
    RU91838U1|2009-08-10|2010-03-10|Федеральное агентство по науке и инновациям |WEARABLE TELECOMMUNICATION COMPLEX OF MONITORING THE FUNCTIONAL STATE OF A HUMAN|
    US8340578B2|2009-10-05|2012-12-25|Apple Inc.|Methods and apparatus for enhanced coexistence algorithms in wireless systems|US10335060B1|2010-06-19|2019-07-02|Dp Technologies, Inc.|Method and apparatus to provide monitoring|
    US9192326B2|2011-07-13|2015-11-24|Dp Technologies, Inc.|Sleep monitoring system|
    CN102387508B|2011-11-01|2019-05-24|中兴通讯股份有限公司|The method and apparatus of carrier wave polymerization in a kind of lte-a system|
    CN103999529B|2011-12-05|2018-07-17|皇家飞利浦有限公司|Electronic key for medical body area network in hospitalsystem transmits solution|
    US9459597B2|2012-03-06|2016-10-04|DPTechnologies, Inc.|Method and apparatus to provide an improved sleep experience by selecting an optimal next sleep state for a user|
    US10791986B1|2012-04-05|2020-10-06|Dp Technologies, Inc.|Sleep sound detection system and use|
    JP5958125B2|2012-07-05|2016-07-27|富士通株式会社|Wireless communication apparatus and control method|
    US9474876B1|2012-12-14|2016-10-25|DPTechnologies, Inc.|Sleep aid efficacy|
    US9594354B1|2013-04-19|2017-03-14|Dp Technologies, Inc.|Smart watch extended system|
    US10022086B1|2013-04-19|2018-07-17|Dp Technologies, Inc.|Extended band system|
    EP3014918B1|2013-06-28|2017-10-04|Koninklijke Philips N.V.|Mban channel management scheme using patient acuity information|
    KR101816567B1|2013-11-12|2018-02-21|한국전자통신연구원|Method and apparatus of interference avoidance based on multi transmission and reception|
    EP3123770B1|2014-03-25|2018-05-16|Koninklijke Philips N.V.|Multi-channel communication scheme for medical body area networkto meet duty cycle regulation|
    WO2015190535A1|2014-06-10|2015-12-17|株式会社 東芝|Integrated circuit for wireless communication, wireless communication terminal, and wireless communication method|
    WO2016016594A1|2014-07-30|2016-02-04|Kabushiki Kaisha Toshiba|Configuring mac parameters in body area networks|
    JP2016046726A|2014-08-25|2016-04-04|富士通株式会社|Ban system, terminal device, ban communication method, and ban communication program|
    US9924514B2|2014-12-30|2018-03-20|SiTune Corporation|Channel selection for concurrent communications between wireless devices|
    US9628168B2|2015-02-26|2017-04-18|Space Systems/Loral, Llc|Dynamic link adaption and/or dynamic allocation of communication resources of a communication system based on external interference information received from external interference information sources|
    US9549387B2|2015-05-29|2017-01-17|Apple Inc.|Techniques for reducing interference in communications using conducted RF links|
    US20170079585A1|2015-09-22|2017-03-23|Medtronic, Inc.|System and method for interacting with an implantable medical device|
    US10673603B2|2015-10-23|2020-06-02|Taiwan Semiconductor Manufacturing Company, Ltd.|Integrated circuit with radio frequency interconnect|
    US10230491B2|2015-12-15|2019-03-12|General Electric Company|System and method for communication in a body area network system|
    FR3049809B1|2016-03-29|2018-04-20|Sagemcom Energy & Telecom Sas|METHOD FOR MANAGING THE ALLOCATION OF CARRIER FREQUENCIES|
    US11024064B2|2017-02-24|2021-06-01|Masimo Corporation|Augmented reality system for displaying patient data|
    WO2018208616A1|2017-05-08|2018-11-15|Masimo Corporation|System for pairing a medical system to a network controller by use of a dongle|
    US10477406B2|2017-09-20|2019-11-12|Motorola Solutions, Inc.|Device, system and method for dynamic channel assignment|
    WO2021134650A1|2019-12-31|2021-07-08|深圳迈瑞生物医疗电子股份有限公司|Wireless communication device|
    WO2021236948A1|2020-05-22|2021-11-25|Lifelens Technologies, Inc.|Gateway device facilitating collection and management of data from a body area network to a study coordinating system|
    WO2022045875A1|2020-08-28|2022-03-03|Mimos Berhad|System and method for qualitative internet of things communications|
    法律状态:
    2020-07-28| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-09-01| B25D| Requested change of name of applicant approved|Owner name: KONINKLIJKE PHILIPS N.V. (NL) |
    2020-09-24| B25G| Requested change of headquarter approved|Owner name: KONINKLIJKE PHILIPS N.V. (NL) |
    2020-11-24| B11B| Dismissal acc. art. 36, par 1 of ipl - no reply within 90 days to fullfil the necessary requirements|
    2021-11-03| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    优先权:
    申请号 | 申请日 | 专利标题
    US32116410P| true| 2010-04-06|2010-04-06|
    US61/321,164|2010-04-06|
    PCT/IB2011/051080|WO2011124995A1|2010-04-06|2011-03-15|Centralized dynamic channel allocation for medical body area networks|
    [返回顶部]